Link reference provider: Improve content-type check#36043
Merged
Conversation
… with text/html Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
mejo-
approved these changes
Jan 9, 2023
Member
mejo-
left a comment
mejo-
left a comment
There was a problem hiding this comment.
Code looks good, thanks for tackling this.
Member
Author
|
/backport to stable25 |
szaimen
reviewed
Jan 9, 2023
szaimen
added
4. to release
PVince81
deleted the
fix/36042/link-reference-less-strict-content-type-check
branch
Member
|
/backport to stable25 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #36042
The content-type sometimes contains the charset:
So the link provider check was too strict. We now check it begins with
text/html.